Skip to contentSkip to conversation

32 bit processors / 64 bit processors

DISCUSSION Rick Brown 12 participants 18 messages Oct 21, 2009 – Nov 13, 2009 2 messages not in the archive

lore
Share & tools
lore

Rick Brown

author
#0 lore raw

Hi,

Firstly, I'm trying to understand what exactly characterizes a procesor or an operating system as 32bit / 64 bit. I've read that it means the "native word size" of a machine. But what exactly is that? Register size? Address bus size? Anything else?

Secondly, I'm trying to understand what exactly does a sizeof(int) depend on when we say it is "platform specific". Is it dependent of compiler being 32bit / 64 bit? Or the OS being 32bit / 64 bit? Or the processor being 32 / 64 bit?

Lastly, How are "sizes" of compiler / OS / processor inter related? Here is my understanding. A 32 bit processor can only be running a 32 bit OS. A 64 bit processor may run a 32 or a 64 bit OS. A 32 bit compiler genrates code only to be run on a 32 bit OS; ditto for 64 bit. Is this right?

TIA,

Rick
--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

#1 lore raw
Quoted 8 lines · Rick Brown

Hi,

Firstly, I'm trying to understand what exactly characterizes a procesor or an operating system as 32bit / 64 bit. I've read that it means the "native word size" of a machine. But what exactly is that? Register size? Address bus size? Anything else?

When they say its 32/64 bit machine its the capability of the system or processor to process so many bits at once !

Quoted 6 lines

Secondly, I'm trying to understand what exactly does a sizeof(int) depend on when we say it is "platform specific". Is it dependent of compiler being 32bit / 64 bit? Or the OS being 32bit / 64 bit? Or the processor being 32 / 64 bit?

its dependent on processor being 32/64 bit

Lastly, How are "sizes" of compiler / OS / processor inter related?

Quoted 2 lines

Here is my understanding. A 32 bit processor can only be running a 32 bit OS.

No ... 32 bit OS can run anything <= 32 bit

Quoted 1 line

A 64 bit processor may run a 32 or a 64 bit OS.

yes thats right !

Quoted 3 lines

A 32 bit
compiler genrates code only to be run on a 32 bit OS; ditto for 64 bit.

Not sure about this let others have their say !

Quoted 3 lines

Is this right?

Please correct me if i am wrong !

Quoted 10 lines

TIA,

Rick

--
To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [email protected] Please read the FAQ at http://kernelnewbies.org/FAQ

Signature · 3 lines
Regards,
~Sid~
I have never met a man so ignorant that i couldn't learn something from him
#2 lore raw
Quoted 6 lines · Siddu

On Wed, Oct 21, 2009 at 8:32 AM, Rick Brown <[email protected]> wrote:
Hi,

Quoted 8 lines

Firstly, I'm trying to understand what exactly characterizes a procesor or an operating system as 32bit / 64 bit. I've read that it means the "native word size" of a machine. But what exactly is that? Register size? Address bus size? Anything else?

When they say its 32/64 bit machine its the capability of the system or processor to process so many bits at once !

I had an understanding of this being how many bits you have to address your RAM.

Quoted 8 lines

Secondly, I'm trying to understand what exactly does a sizeof(int) depend on when we say it is "platform specific". Is it dependent of compiler being 32bit / 64 bit? Or the OS being 32bit / 64 bit? Or the processor being 32 / 64 bit?

its dependent on processor being 32/64 bit

Just did a comparison test but it tells me otherwise. But I'm not sure if the test case if correct, can someone improve it?
On a 64bit CentOS:
[root@yyan ~]# more test.c
#include <stdio.h>

int main ()

{
     printf ("%d\n", sizeof(int));
     return 0;
}

[root@yyan ~]# gcc test.c
[root@yyan ~]# ./a.out
4
[root@yyan ~]# uname -a
Linux yyan.pmlab.com 2.6.18-128.el5 #1 SMP Wed Jan 21 10:41:14 EST 2009 x86_64 x86_64 x86_64 GNU/Linux
[root@yyan ~]#

On my Leopard: (Hopefully it's a 32bit OS as it shows) simonmac:coding yansimon$ cat test.c
#include <stdio.h>

int main ()

{
     printf ("%d\n", sizeof(int));
     return 0;
}

simonmac:coding yansimon$ gcc test.c
simonmac:coding yansimon$ ./a.out
4
simonmac:coding yansimon$ uname -a
Darwin simonmac.local 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386 i386 simonmac:coding yansimon$

Quoted 22 lines

Lastly, How are "sizes" of compiler / OS / processor inter related? Here is my understanding. A 32 bit processor can only be running a 32 bit OS.

No ... 32 bit OS can run anything <= 32 bit

A 64 bit processor may run a 32 or a 64 bit OS.

yes thats right !

A 32 bit
compiler genrates code only to be run on a 32 bit OS; ditto for 64 bit.

Not sure about this let others have their say !
Is this right?

Please correct me if i am wrong !
TIA,

Quoted 16 lines

Rick

--
To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [email protected] Please read the FAQ at http://kernelnewbies.org/FAQ

Signature · 4 lines
Regards,
~Sid~
I have never met a man so ignorant that i couldn't learn something  
from him

--
益牙

http://www.google.com/profiles/simonyanix

--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

#3 lore raw
Quoted 15 lines · 益牙
Quoted 11 lines · Siddu

On Wed, Oct 21, 2009 at 8:32 AM, Rick Brown <[email protected]> wrote:
Hi,

Firstly, I'm trying to understand what exactly characterizes a procesor or an operating system as 32bit / 64 bit. I've read that it means the "native word size" of a machine. But what exactly is that? Register size? Address bus size? Anything else?

Quoted 9 lines
Quoted 3 lines

When they say its 32/64 bit machine its the capability of the system or processor to process so many bits at once !

I had an understanding of this being how many bits you have to address your RAM.

Quoted 2 lines

This is true, but it is also your instruction size. So the native machine code can be 64 bits on a 64bit processor.
- Show quoted text -

Quoted 37 lines
Quoted 8 lines

Secondly, I'm trying to understand what exactly does a sizeof(int) depend on when we say it is "platform specific". Is it dependent of compiler being 32bit / 64 bit? Or the OS being 32bit / 64 bit? Or the processor being 32 / 64 bit?

its dependent on processor being 32/64 bit

Just did a comparison test but it tells me otherwise. But I'm not sure if the test case if correct, can someone improve it?
On a 64bit CentOS:
[root@yyan ~]# more test.c
#include <stdio.h>

int main ()

{
   printf ("%d\n", sizeof(int));
   return 0;
}

[root@yyan ~]# gcc test.c
[root@yyan ~]# ./a.out
4
[root@yyan ~]# uname -a
Linux yyan.pmlab.com 2.6.18-128.el5 #1 SMP Wed Jan 21 10:41:14 EST 2009 x86_64 x86_64 x86_64 GNU/Linux
[root@yyan ~]#

On my Leopard: (Hopefully it's a 32bit OS as it shows) simonmac:coding yansimon$ cat test.c
#include <stdio.h>

int main ()

{
   printf ("%d\n", sizeof(int));
   return 0;
}
Quoted 28 lines

simonmac:coding yansimon$ gcc test.c
simonmac:coding yansimon$ ./a.out
4
simonmac:coding yansimon$ uname -a
Darwin simonmac.local 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386 i386 simonmac:coding yansimon$

Quoted 18 lines

Lastly, How are "sizes" of compiler / OS / processor inter related? Here is my understanding. A 32 bit processor can only be running a 32 bit OS.

No ... 32 bit OS can run anything <= 32 bit

A 64 bit processor may run a 32 or a 64 bit OS.

yes thats right !

A 32 bit
compiler genrates code only to be run on a 32 bit OS; ditto for 64 bit.

Not sure about this let others have their say !
Is this right?

This is dependent on the compiler, or at least the compiler options. This is due to the machine code that the compiler generates.

ie. The difference between x86 machine code and ia64 machine code.

Quoted 33 lines
Quoted 14 lines

Please correct me if i am wrong !
TIA,

Rick

--
To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [email protected] Please read the FAQ at http://kernelnewbies.org/FAQ

Quoted 7 lines

--
Regards,
~Sid~
I have never met a man so ignorant that i couldn't learn something from him

--
益牙

http://www.google.com/profiles/simonyanix

--
To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [email protected] Please read the FAQ at http://kernelnewbies.org/FAQ

#4 lore raw
In reply to 益牙

1. The size of the processor's internal address bus (virtual address space) is what qualifies it as a 32-bit / 64-bit processor. Whether or not the OS changes the processor mode to 64-bit(IA-32e/Long etc) (and thereby has access to the 64-bit virtual address space, extended register set etc) is what qualifies it as a 32-bit / 64-bit OS.

AFAIK, no x86 processor truly supports the complete 64-bit address space (yet) - a. The virtual address space is 64 bits, but still limited by the canonical addressing restriction ( no access to the complete 64-bit virtual address space)
b. The physical address is not 64 bits (no system uses such a large amount of physical memory, so there's no point providing such a large number of address pins out to the memory controller / DRAM)

2. sizeof(int) would be depend on the compiler (which in turn depends on the OS it is compiling for, which in turn depends on what processor it is running on). (Though personally I haven't seen sizeof(int) being anything other than 4 bytes .. but I've seen sizeof(long int) being 64 bits for x86-64 gcc, and 32 bits for i386 gcc)

3. If you consider x86 architecture, since they're always backward compatible, any code you generated for an earlier processor should theoretically run on a newer processor (when the processor in a specific mode). Hence, a 64-bit processor can run a 32-bit OS / 64-bit OS. A 64-bit OS can run programs compiled for 64-bit /32-bit mode(by reverting to a 32-bit mode on the fly). This might not apply to other architectures though.

C

Quoted 109 lines · 益牙
Quoted 6 lines · Siddu

On Wed, Oct 21, 2009 at 8:32 AM, Rick Brown <[email protected]> wrote:
Hi,

Quoted 8 lines

Firstly, I'm trying to understand what exactly characterizes a procesor or an operating system as 32bit / 64 bit. I've read that it means the "native word size" of a machine. But what exactly is that? Register size? Address bus size? Anything else?

When they say its 32/64 bit machine its the capability of the system or processor to process so many bits at once !

I had an understanding of this being how many bits you have to address your RAM.

Quoted 8 lines

Secondly, I'm trying to understand what exactly does a sizeof(int) depend on when we say it is "platform specific". Is it dependent of compiler being 32bit / 64 bit? Or the OS being 32bit / 64 bit? Or the processor being 32 / 64 bit?

its dependent on processor being 32/64 bit

Just did a comparison test but it tells me otherwise. But I'm not sure if the test case if correct, can someone improve it?
On a 64bit CentOS:
[root@yyan ~]# more test.c
#include <stdio.h>

int main ()
{
   printf ("%d\n", sizeof(int));
   return 0;
}
[root@yyan ~]# gcc test.c
[root@yyan ~]# ./a.out
4
[root@yyan ~]# uname -a
Linux yyan.pmlab.com 2.6.18-128.el5 #1 SMP Wed Jan 21 10:41:14 EST 2009 x86_64 x86_64 x86_64 GNU/Linux
[root@yyan ~]#

On my Leopard: (Hopefully it's a 32bit OS as it shows) simonmac:coding yansimon$ cat test.c
#include <stdio.h>

int main ()
{
   printf ("%d\n", sizeof(int));
   return 0;
}
simonmac:coding yansimon$ gcc test.c
simonmac:coding yansimon$ ./a.out
4
simonmac:coding yansimon$ uname -a
Darwin simonmac.local 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386 i386
simonmac:coding yansimon$

Quoted 32 lines

Lastly, How are "sizes" of compiler / OS / processor inter related? Here is my understanding. A 32 bit processor can only be running a 32 bit OS.

No ... 32 bit OS can run anything <= 32 bit

A 64 bit processor may run a 32 or a 64 bit OS.

yes thats right !

A 32 bit
compiler genrates code only to be run on a 32 bit OS; ditto for 64 bit.

Not sure about this let others have their say !
Is this right?

Please correct me if i am wrong !
TIA,

Rick

--
To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [email protected] Please read the FAQ at http://kernelnewbies.org/FAQ

Quoted 6 lines

--
Regards,
~Sid~
I have never met a man so ignorant that i couldn't learn something from him

--
益牙

Quoted 8 lines

http://www.google.com/profiles/simonyanix

--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

#5 lore raw

Hi,

Quoted 2 lines

1. The size of the processor's internal address bus (virtual address space) is what qualifies it as a 32-bit / 64-bit processor.

Well, in that sense, isn't Pentium a "36-bit" processor (since it gives the option of PAE to use 64 GB of memory - it must be having atleast 36 address lines)?

On this topic and in this thread, we have had following responses to the question on what is called a 32-bit or 64-bit processor:

1) Addressable Physical memory (=sizeof(void*))
2) Register Size (=instruction size)

Are the above two independent of each other? If yes, then how do we deine a processor as 32-bit / 64-bit?

Thanks,

Rajat

--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

#6 lore raw

PAE (Physical Address Extension) expands the _physical_ address space to > 32 bits, but the _virtual_ address space stays the same at 32-bits, and the virtual address size is what I mentioned as qualifies the processor as 32-bit or 64-bit.

1. Addressable physical memory / physical address size does not decide whether a processor is 32-bit / 64-bit, there is no processor (AFAIK) which can address 64 bits of physical memory. I suppose sizeof(void*) gives you the size of the _virtual_ address, so yes, I suppose that should be 64 bits on a 64-bit processor (and using a 64-bit compiler)
2. Register size does not decide whether a processor is 32-bit / 64-bit.

C

Quoted 16 lines · Rajat Jain

Hi,

Quoted 2 lines

1. The size of the processor's internal address bus (virtual address space) is what qualifies it as a 32-bit / 64-bit processor.

Well, in that sense, isn't Pentium a "36-bit" processor (since it gives the option of PAE to use 64 GB of memory - it must be having atleast 36 address lines)?

On this topic and in this thread, we have had following responses to the question on what is called a 32-bit or 64-bit processor:

1) Addressable Physical memory (=sizeof(void*))
2) Register Size (=instruction size)

Quoted 8 lines

Are the above two independent of each other? If yes, then how do we deine a processor as 32-bit / 64-bit?

Thanks,

Rajat

--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

#7 lore raw

Hi,

----Original Message----
From: C [mailto:[email protected]]
Sent: Friday, October 23, 2009 10:51 AM
To: Rajat Jain
Cc: [email protected]; Siddu; Rick Brown; kernelnewbies; [email protected]
Subject: Re: 32 bit processors / 64 bit processors

Quoted 4 lines

PAE (Physical Address Extension) expands the _physical_ address space to > 32 bits, but the _virtual_ address space stays the same at 32-bits, and the virtual address size is what I mentioned as qualifies the processor as 32-bit or 64-bit.

Well, IMHO the processor does not decide or even know the size of virtual address space. It purely depends on the software (OS in this case) that runs on it. Consider all of the following is possible on the same 32 bit processor:

1) User may run a firmware on the processor that gives a 1-1 mapping from virtual to physical (thus making virtual address space equal to physical address space).

2) Users may be running different OS(s) that give different amount of virtual address space to use.

What am I missing?

Thanks,

Rajat

Quoted 9 lines

1. Addressable physical memory / physical address size does not decide whether a processor is 32-bit / 64-bit, there is no processor (AFAIK) which can address 64 bits of physical memory. I suppose sizeof(void*) gives you the size of the _virtual_ address, so yes, I suppose that should be 64 bits on a 64-bit processor (and using a 64-bit compiler)
2. Register size does not decide whether a processor is 32-bit / 64-bit.

Quoted 26 lines

C

Quoted 22 lines · Rajat Jain

Hi,

Quoted 2 lines

1. The size of the processor's internal address bus (virtual address space) is what qualifies it as a 32-bit / 64-bit processor.

Well, in that sense, isn't Pentium a "36-bit" processor (since it gives the option of PAE to use 64 GB of memory - it must be having atleast 36 address lines)?

On this topic and in this thread, we have had following responses to the question on what is called a 32-bit or 64-bit processor:

1) Addressable Physical memory (=sizeof(void*))
2) Register Size (=instruction size)

Are the above two independent of each other? If yes, then how do we deine a processor as 32-bit / 64-bit?

Thanks,

Rajat

--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

#8 lore raw
Quoted 2 lines

Well, IMHO the processor does not decide or even know the size of virtual address space.

Ofcourse it does. How else do you think it translates a virtual address to a physical address? Virtual addresses are simply what the software 'sees', the processor takes these, translates them into physical addresses before making any reads / writes to main memory. No software can use a virtual address space larger than what the processor specifies.

Quoted 4 lines

1) User may run a firmware on the processor that gives a 1-1 mapping from virtual to physical (thus making virtual address space equal to physical address space).

Well, I don't know much about other architectures, so I'll just comment on x86. When you switch to 64bit mode, you compulsorily need to have a 4-level paging table, which translates 64-bit linear addresses (actually a 48-bit linear address, since the address is subject to the canonical address requirement) to (upto) 52-bit physical addresses. So irrespective of what firmware you're running, linear addresses are actually 64-bit, but physical addresses are not.

(In fact, physical address space might even be larger than virtual address space, when we take modes like PAE / PSE into account)

Quoted 2 lines

2) Users may be running different OS(s) that give different amount of virtual address space to use.

Irrespective of what OS you're using (and whether it switches to the processor mode that would utilize the 64-bit virtual address space that the processor provides), the 'internal address bus' (virtual address space) of the processor is what decides the maximum virtual address space of any programs that run on it (OS or otherwise).

C

Quoted 11 lines · Rajat Jain

Hi,

----Original Message----
From: C [mailto:[email protected]]
Sent: Friday, October 23, 2009 10:51 AM
To: Rajat Jain
Cc: [email protected]; Siddu; Rick Brown; kernelnewbies; [email protected]
Subject: Re: 32 bit processors / 64 bit processors

Quoted 7 lines
Quoted 4 lines

PAE (Physical Address Extension) expands the _physical_ address space to > 32 bits, but the _virtual_ address space stays the same at 32-bits, and the virtual address size is what I mentioned as qualifies the processor as 32-bit or 64-bit.

Well, IMHO the processor does not decide or even know the size of virtual address space.

Ofcourse it does. How else do you think it translates a virtual address to a physical address?

It purely depends on the software (OS in this

Quoted 7 lines

case) that runs on it. Consider all of the following is possible on the same 32 bit processor:

1) User may run a firmware on the processor that gives a 1-1 mapping from virtual to physical (thus making virtual address space equal to physical address space).

Quoted 46 lines

2) Users may be running different OS(s) that give different amount of virtual address space to use.

What am I missing?

Thanks,

Rajat

Quoted 35 lines

1. Addressable physical memory / physical address size does not decide whether a processor is 32-bit / 64-bit, there is no processor (AFAIK) which can address 64 bits of physical memory. I suppose sizeof(void*) gives you the size of the _virtual_ address, so yes, I suppose that should be 64 bits on a 64-bit processor (and using a 64-bit compiler)
2. Register size does not decide whether a processor is 32-bit / 64-bit.

C

Quoted 22 lines · Rajat Jain

Hi,

Quoted 2 lines

1. The size of the processor's internal address bus (virtual address space) is what qualifies it as a 32-bit / 64-bit processor.

Well, in that sense, isn't Pentium a "36-bit" processor (since it gives the option of PAE to use 64 GB of memory - it must be having atleast 36 address lines)?

On this topic and in this thread, we have had following responses to the question on what is called a 32-bit or 64-bit processor:

1) Addressable Physical memory (=sizeof(void*))
2) Register Size (=instruction size)

Are the above two independent of each other? If yes, then how do we deine a processor as 32-bit / 64-bit?

Thanks,

Rajat

--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#11 lore raw
Quoted 9 lines · nidhi mittal hada

Can someone come and please clarify -- it finally
above chain of mail raises more confusion as conflict stays till end.

1)processor 32/64 bit --
a)data it can process at one instance --- register size --- data
bus size --
OR
b)internal address bus size of processor --- if that is true then
what abt case of pentium 36 bit address lines ---

Of course, register size

Quoted 6 lines

2)OS 32 /64 bit
a)its virtual address space -- what os provides --- to each
process -- which is mapped to physical address space that prcessor provides

Quoted 7 lines

OR
b)processor specifies virtual addr space ??

3)extra ques -- why in case of 32 bit arch -- physical memory RAM limitation comes of 4GB ?

2^32 = 4GB simple...

Quoted 169 lines · On Fri, Oct 23, 2009 at 4:54 PM, <[email protected]…

Hi,

On Thu, 22 Oct 2009 23:58:20 -0700, C <[email protected] <mailto:[email protected]>> wrote:
>> Well, IMHO the processor does not decide or even know the size of >> virtual address space.
> Ofcourse it does. How else do you think it translates a virtual > address to a physical address? Virtual addresses are simply what the > software 'sees', the processor takes these, translates them into > physical addresses before making any reads / writes to main memory. No
> software can use a virtual address space larger than what the > processor specifies.
>
>> 1) User may run a firmware on the processor that gives a 1-1 mapping
>> from virtual to physical (thus making virtual address space equal to
>> physical address space).
>>
> Well, I don't know much about other architectures, so I'll just comment
on
> x86.
> When you switch to 64bit mode, you compulsorily need to have a 4-level
> paging table, which translates 64-bit linear addresses (actually a > 48-bit linear address, since the address is subject to the canonical > address requirement) to (upto) 52-bit physical addresses. So > irrespective of what firmware you're running, linear addresses are > actually 64-bit, but physical addresses are not.
>
> (In fact, physical address space might even be larger than virtual > address space, when we take modes like PAE / PSE into account) >
>> 2) Users may be running different OS(s) that give different amount of
>> virtual address space to use.
> Irrespective of what OS you're using (and whether it switches to the > processor mode that would utilize the 64-bit virtual address space > that the processor provides), the 'internal address bus' (virtual > address space) of the processor is what decides the maximum virtual > address space of any programs that run on it (OS or otherwise). >
> C
>
> On Thu, Oct 22, 2009 at 11:23 PM, Rajat Jain <[email protected] <mailto:[email protected]>> > wrote:
>>
>> Hi,
>>
>> ----Original Message----
>> From: C [mailto:[email protected] <mailto:[email protected]>]
>> Sent: Friday, October 23, 2009 10:51 AM
>> To: Rajat Jain
>> Cc: [email protected] <mailto:[email protected]>; Siddu; Rick Brown; kernelnewbies;
>> [email protected] <mailto:[email protected]> >> Subject: Re: 32 bit processors / 64 bit processors
>>
>>> PAE (Physical Address Extension) expands the _physical_ address space
>>> to > 32 bits, but the _virtual_ address space stays the same at >>> 32-bits, and the virtual address size is what I mentioned as qualifies
>>> the processor as 32-bit or 64-bit.
>>
>> Well, IMHO the processor does not decide or even know the size of >> virtual address space.
> Ofcourse it does. How else do you think it translates a virtual > address to a physical address?
>
> It purely depends on the software (OS in this
>> case) that runs on it. Consider all of the following is possible on the
>> same 32 bit processor:
>>
>> 1) User may run a firmware on the processor that gives a 1-1 mapping
>> from virtual to physical (thus making virtual address space equal to
>> physical address space).
>>
>> 2) Users may be running different OS(s) that give different amount of
>> virtual address space to use.
>>
>> What am I missing?
>>
>> Thanks,
>>
>> Rajat
>>
>>
>>>
>>> 1. Addressable physical memory / physical address size does not decide
>>> whether a processor is 32-bit / 64-bit, there is no processor (AFAIK)
>>> which can address 64 bits of physical memory. I suppose sizeof(void*)
>>> gives you the size of the _virtual_ address, so yes, I suppose that
>>> should be 64 bits on a 64-bit processor (and using a 64-bit compiler)
>>> 2. Register size does not decide whether a processor is 32-bit / >>> 64-bit.
>>>
>>> C
>>>
>>> On Thu, Oct 22, 2009 at 10:05 PM, Rajat Jain
>>> <[email protected] <mailto:[email protected]>> wrote:
>>>>
>>>> Hi,
>>>>
>>>>> 1. The size of the processor's internal address bus (virtual address
>>>>> space) is what qualifies it as a 32-bit / 64-bit processor. >>>>
>>>> Well, in that sense, isn't Pentium a "36-bit" processor (since it >>>> gives the option of PAE to use 64 GB of memory - it must be having
>>>> atleast 36 address lines)?
>>>>
>>>> On this topic and in this thread, we have had following responses to
>>>> the question on what is called a 32-bit or 64-bit processor:
>>>>
>>>> 1) Addressable Physical memory (=sizeof(void*))
>>>> 2) Register Size (=instruction size)
>>>>
>>>> Are the above two independent of each other? If yes, then how do we
>>>> deine a processor as 32-bit / 64-bit?
>>>>
>>>> Thanks,
>>>>
>>>> Rajat
>>
>
> --
> To unsubscribe from this list: send an email with
> "unsubscribe kernelnewbies" to [email protected] <mailto:[email protected]>
> Please read the FAQ at http://kernelnewbies.org/FAQ

>> Well, IMHO the processor does not decide or even know the size of >> virtual address space.

> Ofcourse it does. How else do you think it translates a virtual

No it doesn't... the previous poster is right. (unless we excessively get
into semantics....)
That is up to the MMU, it has absolutely nothing to do with the CPU. And FWIW, x86 is hardly a reference... x86, along with 8051 would have to
be the biggest abonimation
to the concept of elegant processing......

Quoted 19 lines

-- Kris

--
To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [email protected] <mailto:[email protected]>
Please read the FAQ at http://kernelnewbies.org/FAQ

Signature · 5 lines
Thanks & Regards
Nidhi Mittal Hada


*Email Scanned for Virus & Dangerous Content by :* *www.CleanMailGateway.com*

--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

#12 lore raw
In reply to a message not in the archive
Quoted 10 lines · nidhi mittal hada

Can someone come and please clarify -- it finally
above chain of mail raises more confusion as conflict stays till end.

1)processor 32/64 bit --
a)data it can process at one instance --- register size --- data bus
size --
OR
b)internal address bus size of processor --- if that is true then
what abt case of pentium 36 bit address lines ---

A processor is called 32 bit or 64 bit depending on the width of the data bus. not on the register size or data it can process at one instance

for example a 8 bit micro controller can have 16 bit registers. similarly all modern processor has architecture to process more data to increase the throughput.

Quoted 9 lines

2)OS 32 /64 bit
a)its virtual address space -- what os provides --- to each process
-- which is mapped to physical address space that prcessor provides

OR
b)processor specifies virtual addr space ??

dont confuse with virtual addr space with physical addr space . MMU will assist the OS in this issue.

the moment the bit to enable the 64 bit mode is enabled the MMU and other thing are extend to address 64 bit physical addr space.

Quoted 5 lines

3)extra ques -- why in case of 32 bit arch -- physical memory RAM limitation comes of 4GB ?

because the 32 bit can only address 2^32 address location which is 4GB of RAM max. where 2^64 = 16 EB (exa bytes)

finally download some data sheet of different processor and read to get how thing work

Quoted 161 lines · On Fri, Oct 23, 2009 at 4:54 PM, <[email protected]…

Hi,

On Thu, 22 Oct 2009 23:58:20 -0700, C <[email protected] <mailto:[email protected]>> wrote:
>> Well, IMHO the processor does not decide or even know the size of >> virtual address space.
> Ofcourse it does. How else do you think it translates a virtual > address to a physical address? Virtual addresses are simply what the > software 'sees', the processor takes these, translates them into > physical addresses before making any reads / writes to main
memory. No
> software can use a virtual address space larger than what the > processor specifies.
>
>> 1) User may run a firmware on the processor that gives a 1-1 mapping >> from virtual to physical (thus making virtual address space equal to >> physical address space).
>>
> Well, I don't know much about other architectures, so I'll just
comment
on
> x86.
> When you switch to 64bit mode, you compulsorily need to have a
4-level
> paging table, which translates 64-bit linear addresses (actually a > 48-bit linear address, since the address is subject to the canonical > address requirement) to (upto) 52-bit physical addresses. So > irrespective of what firmware you're running, linear addresses are > actually 64-bit, but physical addresses are not.
>
> (In fact, physical address space might even be larger than virtual > address space, when we take modes like PAE / PSE into account) >
>> 2) Users may be running different OS(s) that give different
amount of
>> virtual address space to use.
> Irrespective of what OS you're using (and whether it switches to the > processor mode that would utilize the 64-bit virtual address space > that the processor provides), the 'internal address bus' (virtual > address space) of the processor is what decides the maximum virtual > address space of any programs that run on it (OS or otherwise). >
> C
>
> On Thu, Oct 22, 2009 at 11:23 PM, Rajat Jain
<[email protected] <mailto:[email protected]>>
> wrote:
>>
>> Hi,
>>
>> ----Original Message----
>> From: C [mailto:[email protected]
<mailto:[email protected]>]
>> Sent: Friday, October 23, 2009 10:51 AM
>> To: Rajat Jain
>> Cc: [email protected] <mailto:[email protected]>; Siddu;
Rick Brown; kernelnewbies;
>> [email protected] <mailto:[email protected]> >> Subject: Re: 32 bit processors / 64 bit processors
>>
>>> PAE (Physical Address Extension) expands the _physical_ address
space
>>> to > 32 bits, but the _virtual_ address space stays the same at >>> 32-bits, and the virtual address size is what I mentioned as
qualifies
>>> the processor as 32-bit or 64-bit.
>>
>> Well, IMHO the processor does not decide or even know the size of >> virtual address space.
> Ofcourse it does. How else do you think it translates a virtual > address to a physical address?
>
> It purely depends on the software (OS in this
>> case) that runs on it. Consider all of the following is possible
on the
>> same 32 bit processor:
>>
>> 1) User may run a firmware on the processor that gives a 1-1 mapping >> from virtual to physical (thus making virtual address space equal to >> physical address space).
>>
>> 2) Users may be running different OS(s) that give different
amount of
>> virtual address space to use.
>>
>> What am I missing?
>>
>> Thanks,
>>
>> Rajat
>>
>>
>>>
>>> 1. Addressable physical memory / physical address size does not
decide
>>> whether a processor is 32-bit / 64-bit, there is no processor
(AFAIK)
>>> which can address 64 bits of physical memory. I suppose
sizeof(void*)
>>> gives you the size of the _virtual_ address, so yes, I suppose that >>> should be 64 bits on a 64-bit processor (and using a 64-bit
compiler)
>>> 2. Register size does not decide whether a processor is 32-bit / >>> 64-bit.
>>>
>>> C
>>>
>>> On Thu, Oct 22, 2009 at 10:05 PM, Rajat Jain
>>> <[email protected] <mailto:[email protected]>> wrote:
>>>>
>>>> Hi,
>>>>
>>>>> 1. The size of the processor's internal address bus (virtual
address
>>>>> space) is what qualifies it as a 32-bit / 64-bit processor. >>>>
>>>> Well, in that sense, isn't Pentium a "36-bit" processor (since it >>>> gives the option of PAE to use 64 GB of memory - it must be having >>>> atleast 36 address lines)?
>>>>
>>>> On this topic and in this thread, we have had following
responses to
>>>> the question on what is called a 32-bit or 64-bit processor:
>>>>
>>>> 1) Addressable Physical memory (=sizeof(void*))
>>>> 2) Register Size (=instruction size)
>>>>
>>>> Are the above two independent of each other? If yes, then how
do we
>>>> deine a processor as 32-bit / 64-bit?
>>>>
>>>> Thanks,
>>>>
>>>> Rajat
>>
>
> --
> To unsubscribe from this list: send an email with
> "unsubscribe kernelnewbies" to [email protected]
<mailto:[email protected]>
> Please read the FAQ at http://kernelnewbies.org/FAQ

>> Well, IMHO the processor does not decide or even know the size of >> virtual address space.

> Ofcourse it does. How else do you think it translates a virtual

No it doesn't... the previous poster is right. (unless we excessively get
into semantics....)
That is up to the MMU, it has absolutely nothing to do with the CPU. And FWIW, x86 is hardly a reference... x86, along with 8051 would have to
be the biggest abonimation
to the concept of elegant processing......

Quoted 15 lines

-- Kris

--
To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [email protected] <mailto:[email protected]>
Please read the FAQ at http://kernelnewbies.org/FAQ

Signature · 2 lines
Thanks & Regards
Nidhi Mittal Hada

--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

#13 lore raw
Quoted 12 lines · hmthalib
Quoted 10 lines · nidhi mittal hada

Can someone come and please clarify -- it finally
above chain of mail raises more confusion as conflict stays till end.

1)processor 32/64 bit --
a)data it can process at one instance --- register size --- data
bus size --
OR
b)internal address bus size of processor --- if that is true
then what abt case of pentium 36 bit address lines ---

Quoted 3 lines

A processor is called 32 bit or 64 bit depending on the width of the data bus. not on the register size or data it can process at one instance

for example a 8 bit micro controller can have 16 bit registers. similarly all modern processor has architecture to process more data to increase the throughput.

What would you call pentium pro.... Its address bus is 36 bits wide, and the external data bus is 64 bits wide

Quoted 218 lines
Quoted 10 lines

2)OS 32 /64 bit
a)its virtual address space -- what os provides --- to each
process -- which is mapped to physical address space that prcessor provides
OR
b)processor specifies virtual addr space ??

dont confuse with virtual addr space with physical addr space . MMU will assist the OS in this issue.

the moment the bit to enable the 64 bit mode is enabled the MMU and other thing are extend to address 64 bit physical addr space.

Quoted 5 lines

3)extra ques -- why in case of 32 bit arch -- physical memory RAM limitation comes of 4GB ?

because the 32 bit can only address 2^32 address location which is 4GB of RAM max. where 2^64 = 16 EB (exa bytes)

finally download some data sheet of different processor and read to get how thing work

Quoted 194 lines · On Fri, Oct 23, 2009 at 4:54 PM, <[email protected]…
    Hi,

    On Thu, 22 Oct 2009 23:58:20 -0700, C <[email protected]
    <mailto:[email protected]>> wrote:
     >> Well, IMHO the processor does not decide or even know the 

size of
>> virtual address space.
> Ofcourse it does. How else do you think it translates a virtual > address to a physical address? Virtual addresses are simply
what the
> software 'sees', the processor takes these, translates them into > physical addresses before making any reads / writes to main
memory. No
> software can use a virtual address space larger than what the > processor specifies.
>
>> 1) User may run a firmware on the processor that gives a 1-1
mapping
>> from virtual to physical (thus making virtual address space
equal to
>> physical address space).
>>
> Well, I don't know much about other architectures, so I'll just
comment
on
> x86.
> When you switch to 64bit mode, you compulsorily need to have a
4-level
> paging table, which translates 64-bit linear addresses
(actually a
> 48-bit linear address, since the address is subject to the
canonical
> address requirement) to (upto) 52-bit physical addresses. So > irrespective of what firmware you're running, linear addresses
are
> actually 64-bit, but physical addresses are not.
>
> (In fact, physical address space might even be larger than
virtual
> address space, when we take modes like PAE / PSE into account) >
>> 2) Users may be running different OS(s) that give different
amount of
>> virtual address space to use.
> Irrespective of what OS you're using (and whether it switches
to the
> processor mode that would utilize the 64-bit virtual address
space
> that the processor provides), the 'internal address bus' (virtual > address space) of the processor is what decides the maximum
virtual

     > address space of any programs that run on it (OS or otherwise).
     >
     > C
     >
     > On Thu, Oct 22, 2009 at 11:23 PM, Rajat Jain
    <[email protected] <mailto:[email protected]>>
     > wrote:
     >>
     >> Hi,
     >>
     >> ----Original Message----
     >> From: C [mailto:[email protected]
    <mailto:[email protected]>]
     >> Sent: Friday, October 23, 2009 10:51 AM
     >> To: Rajat Jain
     >> Cc: [email protected] <mailto:[email protected]>; Siddu;
    Rick Brown; kernelnewbies;
     >> [email protected] 

<mailto:[email protected]>
>> Subject: Re: 32 bit processors / 64 bit processors >>
>>> PAE (Physical Address Extension) expands the _physical_ address
space
>>> to > 32 bits, but the _virtual_ address space stays the same at >>> 32-bits, and the virtual address size is what I mentioned as
qualifies
>>> the processor as 32-bit or 64-bit.
>>
>> Well, IMHO the processor does not decide or even know the
size of
>> virtual address space.
> Ofcourse it does. How else do you think it translates a virtual > address to a physical address?
>
> It purely depends on the software (OS in this
>> case) that runs on it. Consider all of the following is possible
on the
>> same 32 bit processor:
>>
>> 1) User may run a firmware on the processor that gives a 1-1
mapping
>> from virtual to physical (thus making virtual address space
equal to

     >> physical address space).
     >>
     >> 2) Users may be running different OS(s) that give different
    amount of
     >> virtual address space to use.
     >>
     >> What am I missing?
     >>
     >> Thanks,
     >>
     >> Rajat
     >>
     >>
     >>>
     >>> 1. Addressable physical memory / physical address size does not
    decide
     >>> whether a processor is 32-bit / 64-bit, there is no processor
    (AFAIK)
     >>> which can address 64 bits of physical memory. I suppose
    sizeof(void*)
     >>> gives you the size of the _virtual_ address, so yes, I 

suppose that
>>> should be 64 bits on a 64-bit processor (and using a 64-bit
compiler)
>>> 2. Register size does not decide whether a processor is
32-bit /

     >>> 64-bit.
     >>>
     >>> C
     >>>
     >>> On Thu, Oct 22, 2009 at 10:05 PM, Rajat Jain
     >>> <[email protected] <mailto:[email protected]>> 
wrote:
     >>>>
     >>>> Hi,
     >>>>
     >>>>> 1. The size of the processor's internal address bus (virtual
    address
     >>>>> space) is what qualifies it as a 32-bit / 64-bit processor.
     >>>>
     >>>> Well, in that sense, isn't Pentium a "36-bit" processor 
(since it
     >>>> gives the option of PAE to use 64 GB of memory - it must be 
having
     >>>> atleast 36 address lines)?
     >>>>
     >>>> On this topic and in this thread, we have had following
    responses to
     >>>> the question on what is called a 32-bit or 64-bit processor:
     >>>>
     >>>> 1) Addressable Physical memory (=sizeof(void*))
     >>>> 2) Register Size (=instruction size)
     >>>>
     >>>> Are the above two independent of each other? If yes, then how
    do we
     >>>> deine a processor as 32-bit / 64-bit?
     >>>>
     >>>> Thanks,
     >>>>
     >>>> Rajat
     >>
     >
     > --
     > To unsubscribe from this list: send an email with
     > "unsubscribe kernelnewbies" to [email protected]
    <mailto:[email protected]>
     > Please read the FAQ at http://kernelnewbies.org/FAQ



     >> Well, IMHO the processor does not decide or even know the 

size of
>> virtual address space.

> Ofcourse it does. How else do you think it translates a virtual

No it doesn't... the previous poster is right. (unless we excessively get
into semantics....)
That is up to the MMU, it has absolutely nothing to do with the CPU. And FWIW, x86 is hardly a reference... x86, along with 8051 would have to
be the biggest abonimation
to the concept of elegant processing......

-- Kris

--
To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [email protected] <mailto:[email protected]>
Please read the FAQ at http://kernelnewbies.org/FAQ

Quoted 15 lines
Quoted 3 lines
Signature · 2 lines
Thanks & Regards
Nidhi Mittal Hada
Signature · 7 lines
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to [email protected]
Please read the FAQ at http://kernelnewbies.org/FAQ



Email Scanned for Virus & Dangerous Content by : www.CleanMailGateway.com

--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

#14 lore raw
Quoted 15 lines · vkm
Quoted 12 lines · hmthalib
Quoted 10 lines · nidhi mittal hada

Can someone come and please clarify -- it finally
above chain of mail raises more confusion as conflict stays till end.

1)processor 32/64 bit --
a)data it can process at one instance --- register size --- data
bus size --
OR
b)internal address bus size of processor --- if that is true
then what abt case of pentium 36 bit address lines ---

Quoted 5 lines
Quoted 3 lines

A processor is called 32 bit or 64 bit depending on the width of the data bus. not on the register size or data it can process at one instance

for example a 8 bit micro controller can have 16 bit registers. similarly all modern processor has architecture to process more data to increase the throughput.

What would you call pentium pro.... Its address bus is 36 bits wide, and the external data bus is 64 bits wide

Oh, you mean I am saying pentium pro as processor, I didn't meant that. so to make clear i will use term SoC today what we get from the semiconductor vendor is SoC may be you have ARM, PowerPC, x86, ia64, AMD , etc... what ever you buy from market is a SoC.

your actual processor will site in one corner or your SoC, where there will be other peripherals along the actual processor, because of Multi core core era we call it as core , did you got it now.

A processor is just has ALU, Register, control unit, PC , etc.. it is where the actual processing takes palace. there will be data/addr bus connecting all the needed modules which also connects the main memory directly or though cache. when data is move to any registers form memory at a time a 32bit processor will move 32bit to a register. even the register is 64bit or 128bit wide the data will be done in multiple processor cycles.

To know more about memory management which done in modern CPU though MMU check the below link

http://duartes.org/gustavo/blog/post/anatomy-of-a-program-in-memory

Quoted 234 lines
Quoted 233 lines
Quoted 10 lines

2)OS 32 /64 bit
a)its virtual address space -- what os provides --- to each
process -- which is mapped to physical address space that prcessor provides
OR
b)processor specifies virtual addr space ??

dont confuse with virtual addr space with physical addr space . MMU will assist the OS in this issue.

the moment the bit to enable the 64 bit mode is enabled the MMU and other thing are extend to address 64 bit physical addr space.

Quoted 5 lines

3)extra ques -- why in case of 32 bit arch -- physical memory RAM limitation comes of 4GB ?

because the 32 bit can only address 2^32 address location which is 4GB of RAM max. where 2^64 = 16 EB (exa bytes)

finally download some data sheet of different processor and read to get how thing work

Quoted 197 lines · On Fri, Oct 23, 2009 at 4:54 PM, <[email protected]…
    Hi,

    On Thu, 22 Oct 2009 23:58:20 -0700, C <[email protected]
    <mailto:[email protected]>> wrote:
     >> Well, IMHO the processor does not decide or even know the 

size of
>> virtual address space.
> Ofcourse it does. How else do you think it translates a virtual > address to a physical address? Virtual addresses are simply
what the
> software 'sees', the processor takes these, translates them into > physical addresses before making any reads / writes to main
memory. No
> software can use a virtual address space larger than what the > processor specifies.
>
>> 1) User may run a firmware on the processor that gives a 1-1
mapping
>> from virtual to physical (thus making virtual address space
equal to
>> physical address space).
>>
> Well, I don't know much about other architectures, so I'll just
comment
on
> x86.
> When you switch to 64bit mode, you compulsorily need to have a
4-level
> paging table, which translates 64-bit linear addresses
(actually a
> 48-bit linear address, since the address is subject to the
canonical
> address requirement) to (upto) 52-bit physical addresses. So > irrespective of what firmware you're running, linear addresses
are
> actually 64-bit, but physical addresses are not.
>
> (In fact, physical address space might even be larger than
virtual
> address space, when we take modes like PAE / PSE into account) >
>> 2) Users may be running different OS(s) that give different
amount of
>> virtual address space to use.
> Irrespective of what OS you're using (and whether it switches
to the
> processor mode that would utilize the 64-bit virtual address
space
> that the processor provides), the 'internal address bus' (virtual > address space) of the processor is what decides the maximum
virtual

     > address space of any programs that run on it (OS or otherwise).
     >
     > C
     >
     > On Thu, Oct 22, 2009 at 11:23 PM, Rajat Jain
    <[email protected] <mailto:[email protected]>>
     > wrote:
     >>
     >> Hi,
     >>
     >> ----Original Message----
     >> From: C [mailto:[email protected]
    <mailto:[email protected]>]
     >> Sent: Friday, October 23, 2009 10:51 AM
     >> To: Rajat Jain
     >> Cc: [email protected] <mailto:[email protected]>; Siddu;
    Rick Brown; kernelnewbies;
     >> [email protected] 

<mailto:[email protected]>
>> Subject: Re: 32 bit processors / 64 bit processors >>
>>> PAE (Physical Address Extension) expands the _physical_ address
space
>>> to > 32 bits, but the _virtual_ address space stays the same at >>> 32-bits, and the virtual address size is what I mentioned as
qualifies
>>> the processor as 32-bit or 64-bit.
>>
>> Well, IMHO the processor does not decide or even know the
size of
>> virtual address space.
> Ofcourse it does. How else do you think it translates a virtual > address to a physical address?
>
> It purely depends on the software (OS in this
>> case) that runs on it. Consider all of the following is possible
on the
>> same 32 bit processor:
>>
>> 1) User may run a firmware on the processor that gives a 1-1
mapping
>> from virtual to physical (thus making virtual address space
equal to

     >> physical address space).
     >>
     >> 2) Users may be running different OS(s) that give different
    amount of
     >> virtual address space to use.
     >>
     >> What am I missing?
     >>
     >> Thanks,
     >>
     >> Rajat
     >>
     >>
     >>>
     >>> 1. Addressable physical memory / physical address size does not
    decide
     >>> whether a processor is 32-bit / 64-bit, there is no processor
    (AFAIK)
     >>> which can address 64 bits of physical memory. I suppose
    sizeof(void*)
     >>> gives you the size of the _virtual_ address, so yes, I 

suppose that
>>> should be 64 bits on a 64-bit processor (and using a 64-bit
compiler)
>>> 2. Register size does not decide whether a processor is
32-bit /

     >>> 64-bit.
     >>>
     >>> C
     >>>
     >>> On Thu, Oct 22, 2009 at 10:05 PM, Rajat Jain
     >>> <[email protected] <mailto:[email protected]>> 
wrote:
     >>>>
     >>>> Hi,
     >>>>
     >>>>> 1. The size of the processor's internal address bus (virtual
    address
     >>>>> space) is what qualifies it as a 32-bit / 64-bit processor.
     >>>>
     >>>> Well, in that sense, isn't Pentium a "36-bit" processor 
(since it
     >>>> gives the option of PAE to use 64 GB of memory - it must be 
having
     >>>> atleast 36 address lines)?
     >>>>
     >>>> On this topic and in this thread, we have had following
    responses to
     >>>> the question on what is called a 32-bit or 64-bit processor:
     >>>>
     >>>> 1) Addressable Physical memory (=sizeof(void*))
     >>>> 2) Register Size (=instruction size)
     >>>>
     >>>> Are the above two independent of each other? If yes, then how
    do we
     >>>> deine a processor as 32-bit / 64-bit?
     >>>>
     >>>> Thanks,
     >>>>
     >>>> Rajat
     >>
     >
     > --
     > To unsubscribe from this list: send an email with
     > "unsubscribe kernelnewbies" to [email protected]
    <mailto:[email protected]>
     > Please read the FAQ at http://kernelnewbies.org/FAQ



     >> Well, IMHO the processor does not decide or even know the 

size of
>> virtual address space.

> Ofcourse it does. How else do you think it translates a virtual

No it doesn't... the previous poster is right. (unless we excessively get
into semantics....)
That is up to the MMU, it has absolutely nothing to do with the CPU. And FWIW, x86 is hardly a reference... x86, along with 8051 would have to
be the biggest abonimation
to the concept of elegant processing......

-- Kris

--
To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [email protected] <mailto:[email protected]>
Please read the FAQ at http://kernelnewbies.org/FAQ

Signature · 2 lines
Thanks & Regards
Nidhi Mittal Hada
Signature · 7 lines
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to [email protected]
Please read the FAQ at http://kernelnewbies.org/FAQ



Email Scanned for Virus & Dangerous Content by : www.CleanMailGateway.com
Signature · 7 lines
Regards,
Mohamed Thalib H
--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
#15 lore raw
In reply to a message not in the archive

Hi,

*1) *a) Processor 32/64 bit defines by :::* Data bus Size*
b) In Pentium 36 bit Adddress, Basically a PAE, Which is Introduced
First by Intel to handle the Demand of RAM more than 4GB, in Heavy
Applications.

*2)* a) 64OS not Run On 32bit Processor, But 32bit OS run on 64Bit Processor by Downgarding its Efficiency of Databus By latching only 32 bit data on 64bit bus by Inserting 32'b0* in MSB of 64Bus...
Processor Generate *Logical* Address, which is Mapped into *Virtual* which in turn Mapped into *Physical*., At low Level For LOW MEMORY Logical Address Directly Mapped to Virtual Address, OS Provides Virtual Address space to a Process,

*3)* *If* Address Bus Size is 32Bit then Possible no. of Permutation that of Address Formed are 2^32 = 4.098 GB.

*Reagrds:*
Pulkit Goel
*mail:* [email protected]

Quoted 179 lines · nidhi mittal hada

Can someone come and please clarify -- it finally
above chain of mail raises more confusion as conflict stays till end.

1)processor 32/64 bit --
a)data it can process at one instance --- register size --- data bus
size --
OR
b)internal address bus size of processor --- if that is true then what
abt case of pentium 36 bit address lines ---

2)OS 32 /64 bit
a)its virtual address space -- what os provides --- to each process --
which is mapped to physical address space that prcessor provides

OR
b)processor specifies virtual addr space ??

3)extra ques -- why in case of 32 bit arch -- physical memory RAM limitation comes of 4GB ?

Quoted 136 lines · On Fri, Oct 23, 2009 at 4:54 PM, <[email protected]> wrote:

Hi,

Quoted 9 lines · On Thu, 22 Oct 2009 23:58:20 -0700, C <[email protected]> wrote:
Quoted 2 lines

Well, IMHO the processor does not decide or even know the size of virtual address space.

Ofcourse it does. How else do you think it translates a virtual address to a physical address? Virtual addresses are simply what the software 'sees', the processor takes these, translates them into physical addresses before making any reads / writes to main memory. No software can use a virtual address space larger than what the processor specifies.

Quoted 5 lines
Quoted 4 lines

1) User may run a firmware on the processor that gives a 1-1 mapping from virtual to physical (thus making virtual address space equal to physical address space).

Well, I don't know much about other architectures, so I'll just comment

on

Quoted 106 lines

x86.
When you switch to 64bit mode, you compulsorily need to have a 4-level paging table, which translates 64-bit linear addresses (actually a 48-bit linear address, since the address is subject to the canonical address requirement) to (upto) 52-bit physical addresses. So irrespective of what firmware you're running, linear addresses are actually 64-bit, but physical addresses are not.

(In fact, physical address space might even be larger than virtual address space, when we take modes like PAE / PSE into account)

Quoted 2 lines

2) Users may be running different OS(s) that give different amount of virtual address space to use.

Irrespective of what OS you're using (and whether it switches to the processor mode that would utilize the 64-bit virtual address space that the processor provides), the 'internal address bus' (virtual address space) of the processor is what decides the maximum virtual address space of any programs that run on it (OS or otherwise).

C

Quoted 11 lines · Rajat Jain

Hi,

----Original Message----
From: C [mailto:[email protected]]
Sent: Friday, October 23, 2009 10:51 AM
To: Rajat Jain
Cc: [email protected]; Siddu; Rick Brown; kernelnewbies; [email protected]
Subject: Re: 32 bit processors / 64 bit processors

Quoted 7 lines
Quoted 4 lines

PAE (Physical Address Extension) expands the _physical_ address space to > 32 bits, but the _virtual_ address space stays the same at 32-bits, and the virtual address size is what I mentioned as qualifies the processor as 32-bit or 64-bit.

Well, IMHO the processor does not decide or even know the size of virtual address space.

Ofcourse it does. How else do you think it translates a virtual address to a physical address?

It purely depends on the software (OS in this

Quoted 7 lines

case) that runs on it. Consider all of the following is possible on the same 32 bit processor:

1) User may run a firmware on the processor that gives a 1-1 mapping from virtual to physical (thus making virtual address space equal to physical address space).

Quoted 46 lines

2) Users may be running different OS(s) that give different amount of virtual address space to use.

What am I missing?

Thanks,

Rajat

Quoted 35 lines

1. Addressable physical memory / physical address size does not decide whether a processor is 32-bit / 64-bit, there is no processor (AFAIK) which can address 64 bits of physical memory. I suppose sizeof(void*) gives you the size of the _virtual_ address, so yes, I suppose that should be 64 bits on a 64-bit processor (and using a 64-bit compiler)
2. Register size does not decide whether a processor is 32-bit / 64-bit.

C

Quoted 22 lines · Rajat Jain

Hi,

Quoted 2 lines

1. The size of the processor's internal address bus (virtual address space) is what qualifies it as a 32-bit / 64-bit processor.

Well, in that sense, isn't Pentium a "36-bit" processor (since it gives the option of PAE to use 64 GB of memory - it must be having atleast 36 address lines)?

On this topic and in this thread, we have had following responses to the question on what is called a 32-bit or 64-bit processor:

1) Addressable Physical memory (=sizeof(void*))
2) Register Size (=instruction size)

Are the above two independent of each other? If yes, then how do we deine a processor as 32-bit / 64-bit?

Thanks,

Rajat

--
To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [email protected] Please read the FAQ at http://kernelnewbies.org/FAQ

Quoted 4 lines
Quoted 2 lines

Well, IMHO the processor does not decide or even know the size of virtual address space.

Ofcourse it does. How else do you think it translates a virtual

No it doesn't... the previous poster is right. (unless we excessively get into semantics....)
That is up to the MMU, it has absolutely nothing to do with the CPU. And FWIW, x86 is hardly a reference... x86, along with 8051 would have to be the biggest abonimation
to the concept of elegant processing......

Quoted 9 lines

-- Kris

--
To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [email protected] Please read the FAQ at http://kernelnewbies.org/FAQ

--
Thanks & Regards
Nidhi Mittal Hada

#16 lore raw

Hi,

What you posted below might hold true for the specific case of Intel CPUs. But that's about it....
The Intel "assumptions" fail on many other CPUs....
Perhaps agree to disagree ? If you only code on x86 PCs, then your assertion just *happens* to be correct....

Conversely - a square is a rectangle, but rectangles are not *necessarily* a square ! We can go round and round I guess....

Best Regards,
Kris
________________________________________
From: Pulkit Goel [mailto:[email protected]]
Sent: Tuesday, 10 November 2009 5:27 AM
To: nidhi mittal hada
Cc: [email protected]; C; [email protected]; Siddu; Rick Brown; kernelnewbies; [email protected]
Subject: Re: 32 bit processors / 64 bit processors

Hi,

1) a) Processor 32/64 bit defines by :::  Data bus Size
    b) In Pentium 36 bit Adddress, Basically a PAE, Which is Introduced First by Intel to handle the Demand of RAM more than    4GB, in Heavy Applications.

2) a) 64OS not Run On 32bit Processor, But 32bit OS run on 64Bit Processor by Downgarding its Efficiency of Databus By latching only 32 bit data on 64bit bus by Inserting 32'b0* in MSB of 64Bus...
Processor Generate Logical Address, which is Mapped into Virtual which in turn Mapped into Physical., At low Level For LOW MEMORY Logical Address Directly Mapped to Virtual Address,  OS Provides Virtual Address space to a Process,

3) If Address Bus Size is 32Bit then Possible no. of Permutation that of Address Formed are 2^32 = 4.098 GB.

Reagrds:
Pulkit Goel
mail: [email protected]
On Fri, Nov 6, 2009 at 5:53 PM, nidhi mittal hada <[email protected]> wrote:
Can someone come and please clarify -- it finally
above chain of mail raises more confusion as conflict stays till end.

1)processor 32/64 bit --
    a)data it can process at one instance --- register size --- data bus size -- OR
    b)internal address bus size of processor ---  if that is true then what abt case of pentium 36 bit address lines ---

2)OS 32 /64 bit
    a)its virtual address space -- what os provides --- to each process -- which is mapped to physical address space that prcessor provides

  OR
     b)processor specifies virtual addr space ??

3)extra ques -- why in case of 32 bit arch -- physical memory RAM limitation comes of 4GB ?

On Fri, Oct 23, 2009 at 4:54 PM, <[email protected]> wrote:
Hi,

Quoted 9 lines · On Thu, 22 Oct 2009 23:58:20 -0700, C <[email protected]> wrote:
Quoted 2 lines

Well, IMHO the processor does not decide or even know the size of virtual address space.

Ofcourse it does. How else do you think it translates a virtual address to a physical address? Virtual addresses are simply what the software 'sees', the processor takes these, translates them into physical addresses before making any reads / writes to main memory. No software can use a virtual address space larger than what the processor specifies.

Quoted 5 lines
Quoted 4 lines

1) User may run a firmware on the processor that gives a 1-1 mapping from virtual to physical (thus making virtual address space equal to physical address space).

Well, I don't know much about other architectures, so I'll just comment

on

Quoted 106 lines

x86.
When you switch to 64bit mode, you compulsorily need to have a 4-level paging table, which translates 64-bit linear addresses (actually a 48-bit linear address, since the address is subject to the canonical address requirement) to (upto) 52-bit physical addresses. So irrespective of what firmware you're running, linear addresses are actually 64-bit, but physical addresses are not.

(In fact, physical address space might even be larger than virtual address space, when we take modes like PAE / PSE into account)

Quoted 2 lines

2) Users may be running different OS(s) that give different amount of virtual address space to use.

Irrespective of what OS you're using (and whether it switches to the processor mode that would utilize the 64-bit virtual address space that the processor provides), the 'internal address bus' (virtual address space) of the processor is what decides the maximum virtual address space of any programs that run on it (OS or otherwise).

C

Quoted 11 lines · Rajat Jain

Hi,

----Original Message----
From: C [mailto:[email protected]]
Sent: Friday, October 23, 2009 10:51 AM
To: Rajat Jain
Cc: [email protected]; Siddu; Rick Brown; kernelnewbies; [email protected]
Subject: Re: 32 bit processors / 64 bit processors

Quoted 7 lines
Quoted 4 lines

PAE (Physical Address Extension) expands the _physical_ address space to > 32 bits, but the _virtual_ address space stays the same at 32-bits, and the virtual address size is what I mentioned as qualifies the processor as 32-bit or 64-bit.

Well, IMHO the processor does not decide or even know the size of virtual address space.

Ofcourse it does. How else do you think it translates a virtual address to a physical address?

It purely depends on the software (OS in this

Quoted 7 lines

case) that runs on it. Consider all of the following is possible on the same 32 bit processor:

1) User may run a firmware on the processor that gives a 1-1 mapping from virtual to physical (thus making virtual address space equal to physical address space).

Quoted 46 lines

2) Users may be running different OS(s) that give different amount of virtual address space to use.

What am I missing?

Thanks,

Rajat

Quoted 35 lines

1. Addressable physical memory / physical address size does not decide whether a processor is 32-bit / 64-bit, there is no processor (AFAIK) which can address 64 bits of physical memory. I suppose sizeof(void*) gives you the size of the _virtual_ address, so yes, I suppose that should be 64 bits on a 64-bit processor (and using a 64-bit compiler)
2. Register size does not decide whether a processor is 32-bit / 64-bit.

C

Quoted 22 lines · Rajat Jain

Hi,

Quoted 2 lines

1. The size of the processor's internal address bus (virtual address space) is what qualifies it as a 32-bit / 64-bit processor.

Well, in that sense, isn't Pentium a "36-bit" processor (since it gives the option of PAE to use 64 GB of memory - it must be having atleast 36 address lines)?

On this topic and in this thread, we have had following responses to the question on what is called a 32-bit or 64-bit processor:

1) Addressable Physical memory (=sizeof(void*))
2) Register Size (=instruction size)

Are the above two independent of each other? If yes, then how do we deine a processor as 32-bit / 64-bit?

Thanks,

Rajat

--
To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [email protected] Please read the FAQ at http://kernelnewbies.org/FAQ

Quoted 4 lines
Quoted 2 lines

Well, IMHO the processor does not decide or even know the size of virtual address space.

Ofcourse it does. How else do you think it translates a virtual

No it doesn't... the previous poster is right. (unless we excessively get into semantics....)
That is up to the MMU, it has absolutely nothing to do with the CPU. And FWIW, x86 is hardly a reference... x86, along with 8051 would have to be the biggest abonimation
to the concept of elegant processing......

-- Kris

--
To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [email protected] Please read the FAQ at http://kernelnewbies.org/FAQ

Signature · 9 lines
Thanks & Regards 
Nidhi Mittal Hada



--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to [email protected]
Please read the FAQ at http://kernelnewbies.org/FAQ
#17 lore raw
In reply to Siddu
Quoted 14 lines · Siddu

On Wed, Oct 21, 2009 at 8:32 AM, Rick Brown <[email protected]> wrote:
Hi,

Firstly, I'm trying to understand what exactly characterizes a procesor or an operating system as 32bit / 64 bit. I've read that it
means the "native word size" of a machine. But what exactly is that?
Register size? Address bus size? Anything else?

Quoted 2 lines

When they say its 32/64 bit machine its the capability of the system or processor to process so many bits at once !

Additionally, the virtual memory address is 64 bit. Also the main difference is with sizeof(long int) and sizeof(void *) on both archs.

Quoted 27 lines

Secondly, I'm trying to understand what exactly does a sizeof(int)
depend on when we say it is "platform specific". Is it dependent of
compiler being 32bit / 64 bit? Or the OS being 32bit / 64 bit? Or the
processor being 32 / 64 bit?

its dependent on processor being 32/64 bit

Lastly, How are "sizes" of compiler / OS / processor inter related?
Here is my understanding. A 32 bit processor can only be running a 32
bit OS.

No ... 32 bit OS can run anything <= 32 bit

A 64 bit processor may run a 32 or a 64 bit OS.

yes thats right !

Quoted 8 lines

A 32 bit
compiler genrates code only to be run on a 32 bit OS; ditto for 64
bit.

Not sure about this let others have their say !

Is this right?

It is possible to use the -m32 and -m64 flags with gcc for generating 32/64 bit compatible code.

--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

#18 lore raw
In reply to Rick Brown
Quoted 6 lines · Rick Brown

Hi,

Firstly, I'm trying to understand what exactly characterizes a procesor or an operating system as 32bit / 64 bit. I've read that it means the "native word size" of a machine. But what exactly is that? Register size? Address bus size? Anything else?

depends on the data bus with.

Quoted 4 lines

Secondly, I'm trying to understand what exactly does a sizeof(int) depend on when we say it is "platform specific". Is it dependent of compiler being 32bit / 64 bit? Or the OS being 32bit / 64 bit? Or the processor being 32 / 64 bit?

the sizeof(int) depends on the limits.h which the complier uses.

Quoted 3 lines

Lastly, How are "sizes" of compiler / OS / processor inter related? Here is my understanding. A 32 bit processor can only be running a 32 bit OS. A 64 bit processor may run a 32 or a 64 bit OS.

The 64bit processor gives you the option to run in 32 bit mode or 64bit mode. there should be register to switch between them. so refer the corresponding data sheet for that processor.

A 32 bit

Quoted 2 lines

compiler generates code only to be run on a 32 bit OS; ditto for 64 bit. Is this right?

yes .

Quoted 11 lines

TIA,

Rick

--
To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [email protected] Please read the FAQ at http://kernelnewbies.org/FAQ

--
Thalib

--
To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [email protected] Please read the FAQ at http://kernelnewbies.org/FAQ

#19 lore raw
In reply to Rick Brown
Quoted 4 lines

Firstly, I'm trying to understand what exactly characterizes a procesor or an operating system as 32bit / 64 bit. I've read that it means the "native word size" of a machine. But what exactly is that? Register size? Address bus size? Anything else?

I've always used the virtual address space as the basis of whether a chip is 32bit or 64bit. On the x86 PAE throws a wrinkle into that but the system is IMO still 32bit.

Quoted 4 lines

Secondly, I'm trying to understand what exactly does a sizeof(int) depend on when we say it is "platform specific". Is it dependent of compiler being 32bit / 64 bit? Or the OS being 32bit / 64 bit? Or the processor being 32 / 64 bit?

Can't answer that one as I don't write a lot of code outside of PHP/Perl.

Quoted 5 lines

Lastly, How are "sizes" of compiler / OS / processor inter related? Here is my understanding. A 32 bit processor can only be running a 32 bit OS. A 64 bit processor may run a 32 or a 64 bit OS. A 32 bit compiler generates code only to be run on a 32 bit OS; ditto for 64 bit. Is this right?

Yes and no. A 32bit OS can only run 32bit apps. On 64bit it depends. The x86-64/amd64 running a 64bit OS can run 64 or 32bit apps with the right libraries. The IA64(Itanium) does not have an option to run 32bit apps. Sparc is whole another ballgame altogether as they have 32bit, 64bit, and 64/32bit.

Signature · 9 lines
Drew

"Nothing in life is to be feared. It is only to be understood."
--Marie Curie
--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs